The version of Apple iOS running on the mobile device is prior to 16.3. It is, therefore, affected by multiple vulnerabilities, including:

  - A vulnerability in the kernel that may result in an app being able to execute code with kernel     privileges. (CVE-2023-23504)

  - Multiple vulenrabilities in Webkit whereby processing maliciously crafted web content my result in     arbitrary code execution. (CVE-2023-23496, CVE-2023-23517, CVE-2023-23518)

  - A vulnerability in ImageIO where processing an image may lead to a denial of service. (CVE-2023-23519)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote host is running a version of macOS / Mac OS X that is 12.x prior to 12.6.3. It is, therefore, affected by multiple vulnerabilities:

  - This issue was addressed by enabling hardened runtime. This issue is fixed in macOS Monterey 12.6.3, macOS     Ventura 13.2, watchOS 9.3, macOS Big Sur 11.7.3, tvOS 16.3, iOS 16.3 and iPadOS 16.3. An app may be able     to access user-sensitive data. (CVE-2023-23499)

  - When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to     ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle     previously was used to issue a `PUT` request which used that callback. This flaw may surprise the     application and cause it to misbehave and either send off the wrong data or use memory after free or     similar in the subsequent `POST` request. The problem exists in the logic for a reused handle when it is     changed from a PUT to a POST. (CVE-2022-32221)

  - curl can be told to parse a `.netrc` file for credentials. If that file endsin a line with 4095     consecutive non-white space letters and no newline, curlwould first read past the end of the stack-based     buffer, and if the readworks, write a zero byte beyond its boundary.This will in most cases cause a     segfault or similar, but circumstances might also cause different outcomes.If a malicious user can provide     a custom netrc file to an application or otherwise affect its contents, this flaw could be used as denial-     of-service. (CVE-2022-35260)

  - curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a non-     HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to the proxy, and     then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often     only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200     status code to the client. Due to flaws in the error/cleanup handling, this could trigger a double free in     curl if one of the following schemes were used in the URL for the transfer: dict, gopher, gophers, ldap,     ldaps, rtmp, rtmps, or telnet. The earliest affected version is 7.77.0. (CVE-2022-42915)

  - In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS     support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step)     even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL     uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion, e.g., using     the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of U+002E (.).
    The earliest affected version is 7.77.0 2021-05-26. (CVE-2022-42916)

  - When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control     codes that when later are sent back to a HTTPserver might make the server return 400 responses.
    Effectively allowing asister site to deny service to all siblings. (CVE-2022-35252)

  - A buffer overflow issue was addressed with improved memory handling. This issue is fixed in macOS Big Sur     11.7.3, macOS Ventura 13.2, macOS Monterey 12.6.3. Mounting a maliciously crafted Samba network share may     lead to arbitrary code execution. (CVE-2023-23513)

  - A logic issue was addressed with improved state management. This issue is fixed in macOS Ventura 13.2,     macOS Monterey 12.6.3. An encrypted volume may be unmounted and remounted by a different user without     prompting for the password. (CVE-2023-23493)

  - A type confusion issue was addressed with improved checks. This issue is fixed in macOS Ventura 13. An app     may be able to execute arbitrary code with kernel privileges. (CVE-2022-32915)

  - The issue was addressed with improved bounds checks. This issue is fixed in macOS Monterey 12.6.3, macOS     Ventura 13.2. An app may be able to execute arbitrary code with kernel privileges. (CVE-2023-23507)

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Big Sur 11.7.3, macOS     Ventura 13.2, macOS Monterey 12.6.3. An app may be able to execute arbitrary code with kernel privileges.
    (CVE-2023-23516)

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.3, macOS     Ventura 13.2, watchOS 9.3, iOS 15.7.3 and iPadOS 15.7.3, tvOS 16.3, iOS 16.3 and iPadOS 16.3. An app may     be able to execute arbitrary code with kernel privileges. (CVE-2023-23504)

  - An information disclosure issue was addressed by removing the vulnerable code. This issue is fixed in     macOS Monterey 12.6.3, macOS Ventura 13.2, iOS 16.3 and iPadOS 16.3, tvOS 16.3, watchOS 9.3. An app may be     able to determine kernel memory layout. (CVE-2023-23502)

  - An access issue was addressed with improved access restrictions. This issue is fixed in macOS Monterey     12.6.3, macOS Ventura 13, macOS Big Sur 11.7.3. An app may be able to access mail folder attachments     through a temporary directory used during compression (CVE-2022-42834)

  - A logic issue was addressed with improved state management. This issue is fixed in macOS Big Sur 11.7.3,     macOS Ventura 13.2, macOS Monterey 12.6.3. An app may be able to gain root privileges. (CVE-2023-23497)

  - A privacy issue was addressed with improved private data redaction for log entries. This issue is fixed in     macOS Monterey 12.6.3, macOS Ventura 13.2, watchOS 9.3, macOS Big Sur 11.7.3, iOS 15.7.3 and iPadOS     15.7.3, iOS 16.3 and iPadOS 16.3. An app may be able to access information about a user's contacts.
    (CVE-2023-23505)

  - This issue was addressed by removing the vulnerable code. This issue is fixed in macOS Ventura 13.3, macOS     Monterey 12.6.3, iOS 16.4 and iPadOS 16.4, macOS Big Sur 11.7.3, tvOS 16.4, watchOS 9.4. An app may be     able to access user-sensitive data. (CVE-2023-27931)

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.3, macOS     Ventura 13.2, iOS 16.3 and iPadOS 16.3, tvOS 16.3, watchOS 9.3. An app may be able to bypass Privacy     preferences. (CVE-2023-23511)

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.3, macOS     Ventura 13.2, watchOS 9.3, macOS Big Sur 11.7.3, Safari 16.3, tvOS 16.3, iOS 16.3 and iPadOS 16.3.
    Processing maliciously crafted web content may lead to arbitrary code execution. (CVE-2023-23517,     CVE-2023-23518)

  - The issue was addressed with improved memory handling. This issue is fixed in macOS Big Sur 11.7.3, macOS     Ventura 13.2, macOS Monterey 12.6.3. An app may be able to bypass Privacy preferences. (CVE-2023-23508)

Note that Nessus has not tested for these issues but has instead relied only on the operating system's self-reported version number.

The version of Apple iOS running on the mobile device is prior to 15.7.3. It is, therefore, affected by multiple vulnerabilities:

  - A vulnerability in app may be able to leak sensitive kernel state (CVE-2023-23500)

  - A vulnerability in app may be able to bypass Privacy preferences (CVE-2023-23503)

  - A vulnerability in app may be able to access information about a user’s contacts (CVE-2023-23505)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote host is running a version of macOS / Mac OS X that is 13.x prior to 13.2. It is, therefore, affected by multiple vulnerabilities:

  - When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to     ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle     previously was used to issue a `PUT` request which used that callback. This flaw may surprise the     application and cause it to misbehave and either send off the wrong data or use memory after free or     similar in the subsequent `POST` request. The problem exists in the logic for a reused handle when it is     changed from a PUT to a POST. (CVE-2022-32221)

  - curl can be told to parse a `.netrc` file for credentials. If that file endsin a line with 4095     consecutive non-white space letters and no newline, curlwould first read past the end of the stack-based     buffer, and if the readworks, write a zero byte beyond its boundary.This will in most cases cause a     segfault or similar, but circumstances might also cause different outcomes.If a malicious user can provide     a custom netrc file to an application or otherwise affect its contents, this flaw could be used as denial-     of-service. (CVE-2022-35260)

  - A vulnerability was found in vim and classified as problematic. Affected by this issue is the function     qf_update_buffer of the file quickfix.c of the component autocmd Handler. The manipulation leads to use     after free. The attack may be launched remotely. Upgrading to version 9.0.0805 is able to address this     issue. The name of the patch is d0fab10ed2a86698937e3c3fed2f10bd9bb5e731. It is recommended to upgrade the     affected component. The identifier of this vulnerability is VDB-212324. (CVE-2022-3705)

  - curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a non-     HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to the proxy, and     then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often     only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200     status code to the client. Due to flaws in the error/cleanup handling, this could trigger a double free in     curl if one of the following schemes were used in the URL for the transfer: dict, gopher, gophers, ldap,     ldaps, rtmp, rtmps, or telnet. The earliest affected version is 7.77.0. (CVE-2022-42915)

  - In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS     support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step)     even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL     uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion, e.g., using     the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of U+002E (.).
    The earliest affected version is 7.77.0 2021-05-26. (CVE-2022-42916)

Note that Nessus has not tested for these issues but has instead relied only on the operating system's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
170573	Apple iOS < 16.3 Multiple Vulnerabilities (HT213606)	Nessus	Mobile Devices	1/25/2023	4/8/2024	high
170432	macOS 12.x < 12.6.3 Multiple Vulnerabilities (HT213604)	Nessus	MacOS X Local Security Checks	1/23/2023	1/23/2024	critical
170606	Apple iOS < 15.7.3 Multiple Vulnerabilities (HT213598)	Nessus	Mobile Devices	1/25/2023	4/8/2024	high
170445	macOS 13.x < 13.2 Multiple Vulnerabilities (HT213605)	Nessus	MacOS X Local Security Checks	1/24/2023	9/6/2023	critical

Detections

Analytics

Plugins Search

high

critical

high

critical